* Improve bootstrap and implement what referred as "bootbots" 
  (instead of deleted HTTP download with JSON peer list).
    Rationale: lack of autoupdate of bootstraps is a "tech debt", can be a problem for users.
    Severity: high.
    Difficulty: medium (bootstrap improvements)/high (bootbots side).
    Priority: high.

* Local friend nick <-> key mapping.
    Rationale: remote can impesonate other person by changing nick and status messages.
    Severity: medium.
    Difficulty: TBD (needs investigation if toxcore can store extradata to profile).
    Priority: medium.

* Dynanic refresh interval based on user's recent activity.
    Rationale: reduce CPU use for screen refresh, esp noticeable on VM or ARM SBCs.
    Severity: medium.
    Difficulty: low to medium.
    Priority: medium to high (relatively low hanging fruit).

* Fix compile warnings.
    Rationale: build should happen without warnings, otherwise bugs can be missed.
    Severity: medium.
    Difficulty: low to medium.
    Priority: high.

* Better static analisys - and fix known static analyzier fallouts.
    Rationale: antibug FTW, can improve security.
    Severity: medium to high.
    Difficulty: medium.
    Priority: (high?).

* Clean up some leftovers of removed code.
    Rationale: some useless ugly ifdefs and so on aren't very good thing.
    Severity: low.
    Difficulty: low to medium.
    Priority: medium.

* Take a look what going on with aborted file xfers and lack of resume.
    Rationale: toxic does something really strange as file xfers resume.
    Severity: low.
    Difficulty: medium or high.
    Priority: medium to low (depends on how hard problem is)

* Option to override friend's nickname and remember this.
    Rationale: some friend can try to change nick and try to cause chaos.
    Severity: medium.
    Difficulty: medium to high (depends if toxcore allows extradata for friends)
    Priority: medium.

* Better offline messages support like saving to DB and reloading it.
  This needs investigation if toxcore can add custom extradata to profile.
  If not it, more problematic due to possible data leak (needs encryption)
  Rationale: now offline msg handling not survives client restart.
  Severity: medium
  Priority: TBD (depends on how hard it to implement)

* (Long term) long range relays over RF, etc. Maybe toxcore feature, not toxic.